@HustonCMichael,   Thanks for that. Windows or PC? How did you uninstall? Did you use the cleaner at all or just via the cloud desktop or ?   And you were getting this specific bug?   I have a couple more tests to run, but I was reaching your conclusion: something in the install, not just my preferences or projects.   Stan     ... View more

@Dani_V.,   This morning, related to another issue, I reset preferences by renaming the entire documents\adobe folder and manually deleting the cache folders. When a new project opens in 25.6.2, the Learning workspace has no Text panel, the Text panel is not checked in the Window submenu, and clicking on it does not open it. Changing to the CG workspace results in UXP Panel 2 instead of the Text panel.   In Beta 26.0.0.39, the Learning panel does not have the Text panel open, but it opens if selected in the Window submenu.   Stan   ... View more

@MyerPj,   Yes, puzzling. Lately, I have just been using the Shft when open to get the reset dialogue. And I reset preferences, cache, and plugin loading cache. So to test further, I used my nuclear option: I renamed the entire documents/adobe folder and deleted the cache folders. I delete the entire folder because some preferences are in the Common folder, and when I am testing multiple versions, I generally want them all reset. And at some point, I was convinced that PR will pick up preferences from earlier versions, but that might only be when installing/updating.   Opened 25.6.2 and created new project. Set preferences to Fit to Frame. Add HD and 4K clips. Make sequence from HD. Add 4k to V2. Effect controls show 50%.   Stan           ... View more

@AD___,   I think you are referring to the Text panel.   See this bug report: https://community.adobe.com/t5/premiere-pro-bugs/25-6-2-missing-text-panel-empty-uxp-panels/idi-p/15604156   Possible workaround: Window -> Workspaces -> turn off "Import workspace from project." Change to the Captions and Graphics workspace (or, probably, any workspace with the Text panel that you want). Close PR. Reopen PR and project. Do NOT change workspaces.   Let us know if that helps.   Stan   ... View more

@Dani_V.,   > this is specific to the Text panel only? I think no, but that has been my focus. In a test tonight, a switch from Captions and Graphics Workspace (CG) to the Learning Workspace resulted in "UXP Panel 4" replacing Adobe Stock in the in Project panel group.   > Are you able to close the UXP panels Yes.   > check/select the Text panel in the Window menu when it's deselected Once deselected with a "UXP" panel anywhere, clicking Window -> Text does not open it.   One time, I got the UXP error for the Adobe Stock, and when I switched back to CG, the Text panel was there with no UXP panel, but Text was empty (no captions/transcript tabs), and showed in Window submenu as not open.   Closing and reopening the project does not reset the UXP panel numbers. Closing and opening PR starts fresh.   Opening PR in the CG workspace allows working in it until there is a change of workspace.   I created a new workspace from CG without changing anything. Going back and forth there did not produce the UXP panels.   Stan   ... View more

@Rocksteady Music School,   Wow. So a sentence in the program monitor/sequence view of the transcript does not appear in the captions?   Stan   ... View more

@Peru Bob,   I did not know that CC app reset.   I looked at the uninstall desktop option recently and was surprised to see that its first instruction is "Ensure that you uninstall all Creative Cloud apps from your device. You can uninstall the Creative Cloud desktop app only when you have uninstalled all Creative Cloud apps (such as Photoshop, Illustrator, and Premiere Pro) on your system. " Is that truly necessary?   Stan     ... View more

@Kerstin Ebert,   Took a look in Beta 26.0.0.39. Very nice.   I have my UI/appearance on "Darkest." The new selection differentiation shows much better on "Dark." (Light is just too bright for me!) I don't see a difference on the accessible contrast. So for now, I've changed to Dark to see how I like that generally.   @FPS_Fish,   Can you look at the Beta? If not, I'll post a screenshot.   Stan       ... View more

@Auto7375,   See my response to your feature request: https://community.adobe.com/t5/premiere-pro-ideas/add-encoding-options-utf-8-bom-utf-16-for-marker-export-to-csv/idc-p/15607757#M23373   Are you Windows or Mac? I wonder if operating system (particularly mac vs PC) can effect what PR exports and/or how Excel opens it.   As I say there "What I see, though, is that the new PR export is UTF-8-BOM (25.6.2 and Beta 26.0.0.39) and the old (24.6.5) is UTF-16 LE BOM. A double-click opens UTF-16 LE in Excel as columns, while it opens UTF-8-BOM as a single column." My description above was confusing as to what encoding worked correctly.   Stan   ... View more

@Auto7375,   Upvoted. It is easier to double-click to open in excel. Note that I am running Excel 2013.   What I see, though, is that the new PR export is UTF-8-BOM (25.6.2 and Beta 26.0.0.39) and the old (24.6.5) is UTF-16 LE BOM. A double-click opens UTF-16 LE in Excel as columns, while it opens UTF-8-BOM as a single column.   I am Win11, and I wonder if operating system (particularly mac vs PC) can effect what PR exports and/or how Excel opens it.   A workaround is to open a new book or sheet in Excel, then Data -> Get External Data -> From Text. The text import wizard in Step 1 shows file origin as "65001: Unicode (UTF8)," and a single column. Pick Delimited here, and "My data has headers." In Step 2, use Tab, not comma. You can click Finish here, or set Data Format for each column in Step 3.   Doing the same with a UTF-16 LE BOM file shows file origin as ANSI (Windows), but otherwise works the same.   Stan   ... View more

@andrewb57,   > I believe this damaged my file   Are you getting a damaged file error when you try to open? Can you post a link to your project file - no media needed.   Stan   ... View more

@mattchristensen,   Thanks for the info; makes sense.   In 25.6.2 and Beta 26.0.0.39, I do not see the Apply button. I tried a few things (deselect apply to all automatically, etc), and nothing changes.   Stan   ... View more

@momentum_5568,   The tunnel version is encoding UTF-8-BOM, whereas the other is UTF-16 LE BOM. If I change it, it opens correctly.   Stan       ... View more

@momentum_5568,   I'll look at this again later. Double-click to open in Excel: I see what you see. Makes no sense!   Stan   ... View more

@MyerPj,   I do NOT see it in 25.6.2. I do in Beta build 39.   Win 11 25H2.   Stan   ... View more

Both of your attachments show them in columns.   I am in Beta 26.0.0.39 at the moment. Marker export to csv looks correct to me there.   Stan   ... View more

@josé_5163,   Pardon the long post, but your question is a good one; including the parts you may not be asking specifically!   I have no inside information, but I think that is a "yes." I was unsuccessful in getting the project I was testing to open in anything other than the Beta.   I have posted about how to minimize problems when updating the Beta: https://community.adobe.com/t5/premiere-pro-beta-discussions/new-beta-uninstall-reset-or-just-update/m-p/15577497#M12541   That post assumed you were updating, but does not address whether and when to update. See my "Cautions" when using the Beta here: https://community.adobe.com/t5/premiere-pro-beta-bugs/cannot-install-premiere-pro-beta/idc-p/14848390#M3790   You have no choice but to use the Beta currently, and many users do so regularly with deadline projects.   I would add the following to what I have posted:   Be certain that you have auto-update turned OFF. In the Creative Cloud Desktop, click on your avatar/account -> Preferences -> Apps. You'll see Auto-update. When there is a new build of the Beta, an invitation to update appears. Do NOT click on it. As noted in my "Cautions," stop-your-work-dead-in-its-tracks bugs may occur in any build of the Beta. While they are often fixed before many users realize they are there, they may persist for multiple days. And once you update the Beta, you cannot go back. So stick with a known-good Beta build as much as you can. As I noted in the update practices post, I use a clone of my system drive as a backup to roll-back to a previous version. Currently, through the cloud desktop, you only have the choice of the final build of Beta 25.6 or the latest build of 26.x. So the only way to roll-back to your known-good build is a clone.   I'm just glad the Beta is a working option for the current issues. And it has been working well for me lately.   Stan ... View more

@josé_5163 @danielchisholm,   > "This file contains mask data that cannot be safely processed."    See Fergus' response above: https://community.adobe.com/t5/premiere-pro-bugs/p-premiere-projects-saved-in-v25-6-0-cannot-be-opened-in-other-v25-x-versions/idc-p/15604764#M58450   I finally tried the new tool, and got this message on the user's project I was troubleshooting. I believe the user had worked on this in the Beta version in addition to 25.6.0. Even if you downgrade such a file with one of the other methods described in this thread, you will be unable to open it in 25.6.2. You can open it in the Beta version, in which case, you do not need to downgrade it.   Stan   ... View more

@Rocksteady Music School,   Are you transcribing and then creating captions? Or are you using the single-step option of creating the transcription and captions? The latter occurs when you put untranscribed clips in a sequence, and click "Create captions from transcript" in the Captions tab.   I just tested a known hour-long sample in 24.6.5, 25.6.2, and Beta 26.0.0.39, and compared the transcription from each.    Testing Captions involves another step, so I'm wondering how you created your captions.   Stan   ... View more

@Sumeet Kumar Choubey,   Today it works. I realized it was an .m2ts file (from a Bluray created long ago), and since I was in the Beta, I copied and renamed to .mts. Both files played in PR with audio.   So then I checked it in PR 24.6.5 - worked fine.   And then back to my 25.6.2 project. The .m2ts already in the project played with sound. ?? And the .mts also.   No idea what happened, but I'm certain it didn't work before. Perhaps codecs got registered being used in other programs.   I'll try to get you a link later today.   Stan   ... View more

@Rajive_Thannippara0492,   In addition to Sumeet's suggestions, copying from a Word document can produce problems. Paste first into Notepad. Do you get the correct characters there? Then copy that and paste into PR. I don't think this is the issue, but its a simple test.   Stan       ... View more

@robubble @Averdahl,   Yes, with every update I install, I reset preferences, clear cache, clear plugin loading cache, and create a new project. That's what I test from.   It is possible that I simply have not imported m2ts since forever; but ran across one today doing to drive cleanup, so gave it a go.   Yes, VLC brings its own codec.    Stan       ... View more

@Averdahl,   I see the same as @robubble. Works in VLC player and Beta (26.0.0.39); not in 25.6.2, including Media Browser -> Source Monitor.    System is Win11 Pro 25H2, updated from Win10 originally.   One search result suggests that there is no system location for the codec (even if installed), installed by a device or app. Is that true? And how does PR handle that. It seems odd to me that it works in Beta and not Release.   Stan   ... View more

@Kpay,   See my post here for information about the process: https://community.adobe.com/t5/premiere-pro-discussions/premiere-pro-unable-to-suddenly-translate-subtitles/m-p/15530664#M573912   There is a screenshot of the message you got in the first post of that thread. My guess is that your issue has nothing to do with the captions being in Korean. I comment in another thread that these translation failures may be time limited. For example, I could consistently get failures one evening, but everything was fine the next morning.   So try again the next day?   Stan   ... View more

@siddharth_5851,   The next update for me was Beta 26.0.0.36. I do not get the problem.   Could be mac vs windows or a bug that came and went between 37 and 39.   Or my process of updating to Beta: reset preferences, clear cache, clear plugin loading cache, and create a new project.   Stan   ... View more

@Agrarvolution,   If you can provide a link to a copy of your project, I can take a look.  I'll say that I became convinced that some projects could not be salvaged. But maybe.   I'd prefer a copy of your project before you downgraded the project, but it may not matter. I do not need the media, just the project file.   Stan       ... View more

@Agrarvolution,   In your earlier post, you describe working in 25.6.0 for some time and Beta. https://community.adobe.com/t5/premiere-pro-bugs/p-premiere-projects-saved-in-v25-6-0-cannot-be-opened-in-other-v25-x-versions/idc-p/15599952#M58168   I suspect you have one of the situations I described in my post to Fergus.   Did you provide a link to one of your projects? I think it needs to be one that you edited in 25.6.0 only or both 25.6.0 and Beta.   Stan   ... View more

@Fergus H,   Thanks for the answer and for the longer explanation.   I had suspected that some users could not use the various conversion options since it only changes the project file version number (from 44 to 43) and they had one or more other issues. You appear to be saying that one of those issues was using masking in the Beta, true? If they used masking in 25.6.0 (was that possible? I have assumed yes), that would also prevent a successful conversion?    The sample project file I was testing involved the XML issue of having an empty tag (<>), and resulted in a damaged project error when opened with any version. And when those XML lines were removed, it would open in the Beta, but not any regular versions.   Stan       ... View more

@siddharth_5851,   I don't see Build 37 yet and may not get a chance to update until tomorrow anyway.   PR Beta 26.0.0.36. Win 11 Pro v11 25H2.   My test worked okay.   I'd also open the Progress panel just to be sure that nothing shows there.   Stan   ... View more

I removed the plugins that still showed as active. No change.   Stan   ... View more